Requirements Reuse and Feature Interaction Management

ion and a low reuse potential; while another requirement can be very general, with a of abstraction and thus a higher reuse potential. We identify the following abstraction specific requirements, generic requirements, and domain-requirements frameworks. Domain-specific requirements are requirements that are derived from a certain dom applications and are concerned only with this domain. Therefore, they they cannot be reused in any other domains and applications (e.g. system-specific requirem General requirements are requirements that are with some variations common to different ap one can replace the differentiation part in the requirement with a variable making requirement (e.g., The system shall support saving of email addresses up to X entries.) A domain requirements framework is a framework that provides guidance on how to ge requirements specification document with hookups to facilitate development The first part of our process for requirements reuse starts with the analysis of a group of sy systems that are part of a product line) in a certain domain that have numerous commo them, and thus it is p actual building of a ne of the common platform to build the new system, along with introducing the new require specific system needs. The third part to this process is interaction management of the requirements. This general process framework can be seen in figure (1) and is described the following subsections. 3.1 Phase 1: Elicitation The aim of phase 1 is to create a database of reusable requirements that can be used later a new system. Phase 1 starts with domain analysis during which a team of developers already develo that can be used t analysis is a set of reusable requirements (kernel requirements and/or parameterized req optional requirements) along with a set of rules of usage that the developer has to follo these requirements (e.g. requirements A and B are mutually exclusive). The next step i group of similar requirements into one component (e.g. all reusable requirements re